Labels:text | screenshot OCR: .Encode v2.5 Final r 19 n Italy .A.S.I. (UU-XX-SS-FS)coding engine S. Encode is probably the fastest program capable of turning an executable file into an ascii readable form using UU/XX/SS/FScode algorythmes. The algos were optimized and rewritten in pure Assembler then linked to the main C program. If you are not an archimede user don't mind the ac[f] options. Encoding : Use: S.Encode -exs <Input File> <Output File> Options: Encodes the executable (or data) input file and puts results on 'Output File' Encodes using XXencode Encodes using SSencode Encodes using FSCode Decoding: Use S.Encode -d[f] <Input File> Options: Decodes UU/XX/SS/FScoded files (automatically recogni- zed). The output path:nomefile is stored in the header of the (UU/XX/SS)encoded file (begin mode nomefile) and FSCoded file (!start nomefile) NEW: S. Encode 2.x now support the multidecoding. It's possible to decode more than one UU/XX/SS/FScoded file from a single input text, this is really useful to extract executables from MAGs or capture from usenet and DO NOT MIND the coding used . -df Forces (UU/XX/SS/FS)decoding, useful to decode stuff coded with other (not too standard) utilitieses Only 4 Archimede users: Use: S.Encode -ac[f] <Input File> Options: (UU/XX/SS )decodes a text file captured from 1 or AREAs, just use the NOGRAPHIC option (CGF/12) and a vt100/tty 80 columns terminal. The S.encode decodes the file in 2 pass, the first depures the capture and creates a "'nomefile . Scd' standard encoded file, the second decodes the whole thing . The S.Encode recognizes any transfer troubles refered to the '.Scd' file. Faf Forces (UU/XX/SS)decoding from AREAS C (UU/XX/SS)decodes from CPEs rather than AREAS -cf Forces (UU/XX/SS)decoding from CPEs Archimede gtw x.29 Nua: (0)222 25516044 00 Vdt: 52181 Hitman Italy's [\/]box: HiT Here a benchmark: done with A500 7Mzh, results on ram disk Executable: C1-text Length: 132868 bytes Prg Time Length UUencode 1'51"' 186048 UUdecode 1'37' ' S.Encode -e 0'03' ' 186070 (because of the initial line) S.Encode -d (UU) 0'04'' ...... S.thing about the encoders: JU/XX/SS/FS algoryhmes are essential to using networks for file transfer . When a binary file is sent through a network it first has to be processed into an ascii standard format, since the executable may contain unreadable chars. The encoders do this creating an ascii file that may be mailed out. UUencode: It's world famous an used, was the first encoder made, uses JUencode : base64 but since has not a table to redefine the ascii chars sequence its output may create troubles on many networks, bbses, chats ... S. Encode uses a custom (safe) XXencode : version (100% compatible) . Clone of UUencode but uses a safe table to redefine the standard ascii chars sequence. SSencode : base64 (4/3) fast/safe/compact/efficient. FSCode : base86 (5/4) it produces the SHORTER output, the theoret ical expansion is only 25% but it's slow, uses almost all chars from $21 to $7E so it is the most critical protocol, always use it with care, it may create lots of problems with net trasfer, it does not work on archimede and probably won't work on strange bbs programs .. experiment, if in doubt use a base64 algorithme. I suggest ALWAYS using FSCode for MAGs. The SSencode owner protocol : news , the only thing I can say is that it is good ! I'11 release all C sources soon, so you can port it on every OS, I do not pretend to make it the UUencode replacer, simply if you like it, just use it. (and spread it). SSencode uses 76 columns, I think is the best size to take advantage of 8 of 80 columns terminals without making troubles (try typing a SSencoded text on amiga and you'll get it). SSencode can decode different size (multiple of 4) so you can vary the 76 chars limit keeping the compatibility. SSencode uses the standard UU/XX header so it can retrieve the name, path and protection of the original file. SSencode uses the standard UU word "end\n" for compatibility ... the algo really doesn't need it, I mean the code doesn't SCREAM if the word is missing but LEAVE it if you port the code. SSencode uses a safe set of char, you can encode and decode without troubles on ANY network. SSencode is base64 (4/3) its output is shorter than UU/XX. Tips: S.Encode has a good error checker that can help you correcting any transfer error, anyway you can disable it if the input text was coded with a not standard encoder . Usage: s_encode -df nomefile What? Have ya got a MAG full of good UU/XX/SS/FScoded stuff and R ya tired to extract 'em? Wanna know if latest phrack has published your code but don't wanna examine a 1.2MB text file? Usage: s_encode -d phrack Don't forget using the NOGRAPH option when decoding from CPEs or AREAS, sometime all may be all right but NOT everytime! To forward a decoded text from CPEs or AREAs simply resend the .Scd file (Standard UU/XX/SS), if you notice transfer troubles simply fix the nomefile. Scd and redecode it (using 'd' option NOT 'c' or 'a') Example: s_encode -a capture Pass 1 (this depure from cept 3 graphic) Pass 2 (normal decoding ) Error 10: troubles at line 56 (well, simply edit capture. Scd and fix the line 56 then) s_encode -d capture . Scd (well done) NEVER use FSCode on archimede it DOES NOT work! S.Encode is REALLY easy to use, I could add 100 useless options like other lame encoders but I think this is all you need . rrors: Error 1: input file does not exist Maybe have you mistaken path? Error 2: input file is empty You have tried opening an empty file Error 3: cannot open <file.Scd> Second pass error, . Scd file is locked or you have mistaken path Error 4: Error 4: memory full Expand your amiga Error 5: output file missing Options 'e'x's' require an output file Error 6: invalid option <x> option <x> does not exist Error 7: too many parameters Option 'd' requires only input file Error 8: cannot create the output Output file is locked or you have file mistaken path Error 9: no end line The UU/XXtext don't contain the word end or it's corrupt Error 10: troubles at line <n> The line <n> is corrupt Error 11: input file is not in a You've forgotten the NOGRAPHIC option correct format Error 12: input file is too short or swapped the a/c options Must be at least 100 bytes Error 13: multidecoding interrupted The input file is not ascii or it is not correctly formatted Error 14: crc mismatch FSCode: input file is corrupt Error 15: size mismatch FSCode: input file is corrupt Final stuff: S. Encode is full public domain, you can use, copy, sell it, I really don't care. FsCode credits must go to Flavio Stanchina, I've totally rewritten the code (in C), now it runs 2 times faster, my code il slightly different (ex: I've leaved the file path intact 'cause I like so) but 100% compatible. For BUGS or IDEAs just E-mail to Internet : hit@bix.com if you are paranoid use my PGP key -BEGIN PGP PUBLIC KEY BLOCK Version: 2.3a.2 mQCNA iypAu IAAAEEALVTUHL 14zthwydN+3oydN j?woyokBpi1wBYnKJ40GFa/KT3 faERV90 i fxTS73Ec9pYhS/GSIRUVuOGwahxZUDOH IDgXnoceRamhE1/A9FyS ImJe KMc85+nuDu20THMbx/W+DDHJMR1RpZnBzVPMGE jixon02nE/5xrNm/sb/cUdAAUR tBp IaXRt YW4gSXRhbHkgPGhpdEBiaXgu Y29tPg == =bCu4 -END PGP PUBLIC KEY BLOCK- if you have X.25 access just call QSD nua: (0)208057040540 mbx: Hitman Italy there are other ways you can reach me (VMB/Collect systems/BBSes/PSImail) just lemme know where you are and what you can use .
(.png)
